-
Notifications
You must be signed in to change notification settings - Fork 24.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(common): locales
are not being shipped
#23136
Conversation
@alexeagle can you have a quick look please? Thanks :) |
λ yarn buildifier
yarn run v1.3.2
$ bazel build --noshow_progress @com_github_bazelbuild_buildtools//buildifier
DEBUG: C:/users/alag/appdata/local/temp/_bazel_alag/btbwur4a/external/io_bazel_rules_go/go/private/toolchain.bzl:104:5: mkdir C:\WINDOWS\go-build100047967: Access is denied.
ERROR: C:/users/alag/appdata/local/temp/_bazel_alag/btbwur4a/external/io_bazel_rules_go/go/toolchain/BUILD.bazel:6:1: every rule of type _go_toolchain implicitly depends upon the target '@go_sdk//:packages.txt', but this target could not be found because of: no such package '@go_sdk//': Traceback (most recent call last):
File "C:/users/alag/appdata/local/temp/_bazel_alag/btbwur4a/external/io_bazel_rules_go/go/private/toolchain.bzl", line 45
_prepare(ctx)
File "C:/users/alag/appdata/local/temp/_bazel_alag/btbwur4a/external/io_bazel_rules_go/go/private/toolchain.bzl", line 105, in _prepare
fail("failed to list standard package...")
failed to list standard packages
ERROR: Analysis of target '@com_github_bazelbuild_buildtools//buildifier:buildifier' failed; build aborted: no such package '@go_sdk//': Traceback (most recent call last):
File "C:/users/alag/appdata/local/temp/_bazel_alag/btbwur4a/external/io_bazel_rules_go/go/private/toolchain.bzl", line 45
_prepare(ctx)
File "C:/users/alag/appdata/local/temp/_bazel_alag/btbwur4a/external/io_bazel_rules_go/go/private/toolchain.bzl", line 105, in _prepare
fail("failed to list standard package...")
failed to list standard packages
INFO: Elapsed time: 29.225s
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. After I ran I will get
|
fixed the lint on a mac |
Let's file the issue with rules_go - I don't want to leave Windows broken... Could you try upgrading the Go rules first - change /WORKSPACE to this version So that our issue report is against their current release (or maybe it will be solved by updating) |
Ill try that tomorrow morning, as at the moment I have only my Mac
available.
Ill give it a shot tomorrow and keep you posted.
…On Tue, 03 Apr 2018 at 17:40, Alex Eagle ***@***.***> wrote:
Let's file the issue with rules_go - I don't want to leave Windows
broken...
Could you try upgrading the Go rules first - change /WORKSPACE to this
version
https://github.com/alexeagle/angular-bazel-example/blob/master/WORKSPACE#L65
So that our issue report is against their current release (or maybe it
will be solved by updating)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#23136 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQv-WhNnDQ3wcLpqtQ1taz8AT31nVOvvks5tk5fegaJpZM4TEuWi>
.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
It's simpler than I expected - I thought these nested locales directories needed to appear as entry points. But checking the output from the old build.sh (still published as https://github.com/angular/common-builds) this seems right to me.
Hi @alexeagle & @IgorMinar I relized I did a small mistake I did a nested Any pointers where should I look? PR: #23153 I am really sorry for this guys. But I didn't notice earlier about this mistake and problem, and the tests where not giving an error. |
Hey @alexeagle. As promised I have tried to update the Do you want me to push the go rules update anyways since it’s a step forward? |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: #23140, #23103
What is the new behavior?
locales are shipped
Does this PR introduce a breaking change?
Other information